Update NPEP-133 with Admin-tier restriction and DNS security guidance#366
Update NPEP-133 with Admin-tier restriction and DNS security guidance#366tssurya wants to merge 1 commit into
Conversation
✅ Deploy Preview for kubernetes-sigs-network-policy-api ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: tssurya The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
b8a2a6c to
2af60be
Compare
…nd CEL The PR updates the details around domainNames as discussed in KubeCon Atlanta: https://docs.google.com/document/d/1AtWQy2fNa4qXRag9cCp5_HsefD7bxKe3ea2RPn8jnSs/edit?tab=t.k47ujuef4zxk#bookmark=id.hl0pbdvwfotd - Add CEL validation for Accept-only action restriction - Update API examples to v1alpha2 ClusterNetworkPolicy format - Add Expected Behavior points for DNS reachability and resolv.conf - Add Recommended Behavior section covering DNS security concerns, grace period, and DNSSEC best practice - Add Connection Lifecycle section for policy add/remove semantics
2af60be to
2417bb7
Compare
|
@danwinship PTAL |
| * Currently only `Accept` type rules are proposed. | ||
| * Safely enforcing `Deny` rules based on FQDN selectors is difficult as there | ||
| * Currently only `ACCEPT` type rules are proposed. | ||
| * Safely enforcing `DENY` rules based on FQDN selectors is difficult as there |
There was a problem hiding this comment.
Hm... why did you change these? Especially if they're going to be in backticks, they should be the API values, right?
| * **Policy removal**: Existing established connections SHOULD be allowed to | ||
| complete gracefully. New connections SHOULD be denied after the policy is | ||
| removed. This is consistent with the general NetworkPolicy behavior for | ||
| long-running connections. |
There was a problem hiding this comment.
that's an open question isn't it? #305
I'd just leave out the "policy removal" section. Removing an FQDN policy should behave just like removing any other policy.
The PR updates the details around domainNames
as discussed in KubeCon Atlanta:
https://docs.google.com/document/d/1AtWQy2fNa4qXRag9cCp5_HsefD7bxKe3ea2RPn8jnSs/edit?tab=t.k47ujuef4zxk#bookmark=id.hl0pbdvwfotd
NOTE to reviewers:
*can mean one or more labels and that's what is present in current OKEP as well